Skip to content

[release-4.17] OCPBUGS-61212: Retry SSH server initialization #3256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: release-4.17
Choose a base branch
from
Open

[release-4.17] OCPBUGS-61212: Retry SSH server initialization #3256

wants to merge 1 commit into from

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Sep 3, 2025

This is an automated cherry-pick of #3205

/assign sebsoto

/cherrypick release-4.16

@sebsoto
Retry SSH server initialization
902344b 
Attempts to fix an issue where Windows Server 2019 machines were not
having a running SSH server due to network instability.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 3, 2025
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 3, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60774 has been cloned as Jira Issue OCPBUGS-61212. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-61212: Retry SSH server initialization

In response to this:

This is an automated cherry-pick of #3205

/assign sebsoto

/cherrypick release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.17] OCPBUGS-60774: Retry SSH server initialization [release-4.17] OCPBUGS-61212: Retry SSH server initialization Sep 3, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 3, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 3, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61212, which is invalid:

  • expected dependent Jira Issue OCPBUGS-60774 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #3205

/assign sebsoto

/cherrypick release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 3, 2025
@openshift-ci openshift-ci bot requested review from jrvaldes and sebsoto September 3, 2025 16:06
jrvaldes
jrvaldes approved these changes Sep 3, 2025
View reviewed changes
Copy link
Contributor

@jrvaldes jrvaldes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@jrvaldes
Copy link
Contributor

jrvaldes commented Sep 3, 2025

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/vsphere-proxy-e2e-operator 902344b link true /test vsphere-proxy-e2e-operator
ci/prow/vsphere-e2e-operator 902344b link true /test vsphere-e2e-operator
ci/prow/azure-e2e-operator 902344b link true /test azure-e2e-operator
ci/prow/vsphere-disconnected-e2e-operator 902344b link true /test vsphere-disconnected-e2e-operator
ci/prow/wicd-unit-vsphere 902344b link true /test wicd-unit-vsphere
ci/prow/platform-none-vsphere-e2e-operator 902344b link true /test platform-none-vsphere-e2e-operator

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@wgahnagl
Copy link
Contributor

wgahnagl commented Sep 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 9, 2025

@wgahnagl: This pull request references Jira Issue OCPBUGS-61212, which is invalid:

  • expected dependent Jira Issue OCPBUGS-60774 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sebsoto sebsoto Awaiting requested review from sebsoto

1 more reviewer

@jrvaldes jrvaldes jrvaldes approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@sebsoto sebsoto

@jrvaldes jrvaldes

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@openshift-cherrypick-robot @openshift-ci-robot @jrvaldes @wgahnagl @sebsoto